find_sdk

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description ('Find') is consistent with these and adds no contradictory behavior. However, it provides no additional behavioral context such as result limits or error handling, so it meets the minimum bar given annotation coverage.

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 a single sentence that is immediately informative and free of filler. It is front-loaded with the action verb and resource, making it highly concise and well-structured.

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?

While the tool has annotations and an output schema, the description is too sparse given the context. It does not explain the 'limit' parameter's role or specify how this tool differs from similar siblings like find_examples and search_docs, leaving the description incomplete for an agent to make fully informed decisions.

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 description only implicitly references the 'language' parameter ('for a requested language'). The 'limit' parameter is entirely unexplained, so the description fails to compensate for the schema gap and does not fully clarify parameter meaning.

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 uses the specific verb 'Find' with the resource 'SDK documentation and code examples' and the scope 'for a requested language,' making the core purpose clear. However, it does not explicitly distinguish itself from sibling tools like find_examples or search_docs, so it doesn't fully earn a 5.

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 provides no guidance on when to choose this tool over alternatives. It neither mentions specific use cases nor contrasts with sibling tools, leaving the agent to infer the conditions for use without adequate support.

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