get_php_conf

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing: not whether this is a read-only operation, what scope of configuration is returned, whether it requires elevated permissions, or what the response contains. For a no-annotation tool this is a complete gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words is not conciseness but under-specification; the text is front-loaded but there is essentially no content to structure. Nothing here earns meaningful space because nothing is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one ambiguous parameter, no annotations, no output schema, and a crowded sibling set containing get_php_conf_file and update_php_conf, the description does nothing to make the call actionable or to distinguish this tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole required parameter is a bare number named "id" with no documentation. The description supplies no meaning whatsoever for what this id identifies (a runtime, a website, a config file), so an agent cannot correctly supply it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

"Get PHP config" merely restates the tool name (get_php_conf) without adding a verb-object distinction beyond the token names. It gives no hint of which config is fetched or how it differs from the sibling get_php_conf_file, leaving the agent unable to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as get_php_conf_file or list_php_runtimes. The agent must infer usage purely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.