Get All Custom Schemas

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

Annotations already declare `readOnlyHint=true`, `destructiveHint=false`, and `idempotentHint=true`, so the agent knows this is safe and idempotent. The description adds minimal behavioral context by explaining that it returns all custom schemas and what they are, but does not disclose anything beyond what annotations imply (e.g., no mention of pagination or output format). With annotations handling most of the burden, a score of 3 is appropriate.

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 two sentences, front-loading the primary purpose (returns all custom schemas) and then clarifying the domain (what custom schemas are). Every sentence earns its place with no redundant or extraneous information.

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?

Given the tool has no parameters, no output schema, and the annotations are rich, the description adequately conveys the tool's role. It defines the output concept (all custom schemas) and the entity type. Minor improvement could mention that no filtering or pagination is available, but the description is sufficient for an agent to understand when to select this tool.

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?

The tool has zero parameters and schema coverage is 100%. The description adds meaning by explaining what a custom schema is, which helps the agent understand the return value. Since there are no parameters to document, a baseline of 4 is justified.

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 clearly states it returns all custom schemas, defines what custom schemas are, and the name `get_custom_schemas` (plural) distinguishes it from the singular `get_custom_schema` sibling. This gives the agent a precise understanding of the tool's function.

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?

No guidance is provided on when to use this tool versus alternatives like `get_custom_schema` (singular) or other get-* tools. The description assumes the agent knows to choose this when needing all schemas, but no explicit context or exclusion criteria are given.

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