get_resource_info

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Gets detailed info' with no explanation of what data is returned, any side effects (none expected), or operational characteristics. This is insufficient for an agent to understand the tool's behavior.

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?

The description is extremely short (one sentence), which is concise, but it is under-specified to the point of being unhelpful. It lacks any structure that could convey required information, making the conciseness counterproductive.

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?

For a tool with one parameter, no output schema, and no annotations, the description still fails to provide essential context. It doesn't explain what 'detailed info' means, what the returned data looks like, or how to interpret results. This is inadequate for an agent to decide whether and when to invoke it.

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 single parameter 'resource_path' has no description in the schema. The tool description adds no additional meaning, leaving the agent with no understanding of what constitutes a valid resource_path value (e.g., format, scope, or examples).

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?

The description states a generic verb ('Gets') and a generic resource ('detailed info about a resource'). It is not a tautology, but it is vague and does not specify what 'detailed info' includes or how it differs from sibling tools like list_resources or get_resource_dependencies. An agent cannot tell what this tool uniquely offers.

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 guidance on when to use this tool versus alternatives. No mention of context, prerequisites, or exclusions. With many similar sibling tools (list_resources, get_resource_dependencies, inspect_scene_tree), the lack of usage guidance is a critical gap.

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