Framework & server orientation

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety and side-effect profile is fully covered without description help. The description adds the useful scope fact that the response includes data version and license metadata, but says nothing about freshness guarantees or size of the payload beyond what the output schema supplies.

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?

Three short sentences, front-loaded with the routing instruction 'Start here' before the content list, and zero filler. Every clause carries information the agent needs.

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 zero-parameter tool with an output schema and full annotation coverage, the description supplies what the schema cannot: its role as the server entry point and the fact that it teaches navigation of the other tools. It omits any mention of sibling relationships or follow-up actions, which would round it out.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The explicit 'No parameters.' statement confirms the tool is a no-argument call, adding small but real clarity for an agent deciding whether it needs to gather inputs first.

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 the resource (the framework) and enumerates exactly what is returned: entity counts, data version/crawl date/license, and tool navigation guidance. 'Start here' plus the navigation clause distinguishes it from data-retrieval siblings like search_framework and get_entity, though it never names an alternative explicitly.

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?

'Start here' is an explicit when-to-use instruction that positions the tool as the entry point before the other ten siblings. It gives no when-not-to-use or fallback condition, but for an orientation tool the single directive is clear context.

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