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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context beyond that: results are 'source-backed' and 'coverage and review gaps are reported honestly,' which signals data quality caveats an agent would not infer from annotations alone.

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 short and front-loaded, beginning with what is returned and then adding a quality caveat and invocation note. It avoids waste, though the final sentence is abrupt and could be integrated more clearly.

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?

The tool is a simple read operation with an output schema, so return-value detail is not required. However, the description is incomplete for the crowded sibling landscape because it neither distinguishes job from task nor explains when this retrieval tool is preferable to planning or search alternatives.

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%, so the description must compensate for the two undocumented parameters. It only says 'Pass job or task' without explaining the difference between job and task, whether both may be supplied, or what each is suited for, leaving key semantics unclear.

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 specific verb and resource set: 'Read source-backed approach families, methods, lenses and needed tools.' This tells the agent it retrieves approaches rather than workflows, specialists, or jobs, though it does not explicitly distinguish itself from siblings such as search_library or get_workflow.

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 only guidance is 'Pass job or task,' which explains invocation input but not when to use this tool instead of alternatives. With many sibling retrieval and planning tools, the lack of routing guidance is a significant gap.

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