fedramp_get_definition

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and description adds that it returns actionable error with suggestions if term not found, and case-insensitive matching. No contradictions.

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?

Two concise paragraphs with front-loaded purpose, followed by authoritative context and parameter/return details. Every sentence is necessary and informative without redundancy.

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 simple lookup tool with one parameter and an output schema present, the description fully covers input format, authoritative nature, return structure (definition, ID, aliases, related terms), and error handling. No gaps.

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 input schema already has a clear description for the 'term' parameter (e.g., examples and case-insensitivity), so the tool description adds only marginal extra context (e.g., 'FRD ID', 'alias'). Schema description coverage is reported as 0% but property descriptions exist; assuming actual coverage is higher.

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 clearly states it looks up a FedRAMP defined term by name, alias, or FRD ID. It distinguishes from siblings like 'fedramp_get_document' (for documents) and 'fedramp_get_rule' (for rules) by focusing solely on definitions.

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?

Explicitly notes that definitions are authoritative and part of the rule, giving context for when to use. Provides example inputs and explains return behavior, though does not explicitly list alternatives for when not to use.

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