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

No annotations are provided, so the description must convey behavior. It clearly states the tool uses a local registry without external searches, and optionally narrows by topic/region. However, it does not explicitly state whether the operation is read-only or non-destructive, which would be helpful.

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 concise with two sentences plus an actionable ASRP note. It is front-loaded with the core purpose and immediately useful follow-up instructions, with no superfluous content.

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 discovery tool with no output schema, the description adequately covers the tool's purpose, parameters, and next steps. It lacks details on result format or pagination, but the follow-up tools are referenced. The complexity is low, and the description is sufficient for most use cases.

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 75% (3 of 4 params have descriptions). The description adds context that topic and region are optional filters, but does not provide additional meaning for the 'limit' parameter beyond its schema type and default. The description adds marginal value over the schema.

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 specifies the tool's function as discovering first-hand information sources from the local registry, explicitly stating it does not involve external search engines. It also distinguishes itself from siblings like origingrid_fetch and origingrid_get_source by indicating follow-up actions.

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 explicit guidance on when to use this tool ('FIRST for broad topic discovery') and what to do next ('Follow with origingrid_plan for multi-step fetch or origingrid_fetch for single URL'), including alternatives for different scenarios.

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