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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only safety profile is covered. The description adds valuable behavioral context beyond that: the guides are free ('no payment') and the operation returns only metadata, never bodies. These details help an agent set expectations without contradicting annotations.

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 with no fluff. Purpose is front-loaded, followed by cost and return-type constraints. Every sentence earns its place.

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 description covers purpose, cost, and the metadata-only return constraint, and annotations cover safety. However, with no output schema, the description does not detail what metadata fields are returned or how results are paginated. For a tool with 5 optional parameters, this leaves some room for agent uncertainty about the exact response shape.

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 60%, so the schema documents tag, query, and free_only but leaves limit and category underdocumented. The description adds some indirect parameter context by listing topic areas (which map to categories) and mentioning 'Free — no payment' (relating to free_only), but it doesn't systematically explain parameters. This is adequate but not a strong compensation for the coverage gap.

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?

Description states the specific verb 'Search' plus the resource 'Saylor Innovations technical guides' and lists topic areas. It further distinguishes itself from siblings like get_guide by explicitly saying 'Returns metadata only, never bodies.'

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 the use case—finding technical guides before retrieving them—and the 'never bodies' line hints at a boundary with get_guide. However, it never explicitly says 'use this to discover guides, then call get_guide for full content' or names any alternative. No clear when-not-to-use guidance is provided.

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