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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states it returns a JSON string with detailed information and lists the argument. However, it does not explicitly confirm that the operation is read-only, nor does it mention error behavior or permissions, which are relevant for a tool-fetch operation.

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 front-loaded with the core purpose in the first sentence, followed by focused Args and Returns sections. It is concise and structured, though the phrase 'This tool allows ChatGPT to' is somewhat redundant with the overall tool context.

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 only one parameter and an output schema present, the description covers the basics. It does not specify how to discover valid resource names or handle missing resources, which would be useful for an agent deciding what to fetch. The description is adequate but not fully complete for troubleshooting.

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?

The input schema only defines `resource` as a string with no description. The description compensates by explaining that `resource` is the name of the tool or resource to fetch information about, adding clear meaning. It does not provide examples or valid values, but for a single required parameter, this is sufficient.

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 clear action: 'Fetch detailed information about a specific tool or resource.' It names the resource type and mentions parameters, usage examples, and functionality. It does not explicitly contrast with sibling tools like 'search', but the verb 'fetch' combined with 'detailed information' differentiates it adequately.

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?

The description implies this should be used when detailed information about a tool is needed, but it does not explicitly specify when to prefer this over alternatives or when not to use it. There is no mention of alternatives or exclusions.

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