Get Object Schemas

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

Annotations indicate readOnly/ idempotent; description adds context about account-level schemas and pagination, but doesn't cover potential errors or unusual behavior.

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 sentences, each adding value, starting with purpose, then definition, then usage. No wasted words.

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?

Describes purpose, filtering, and pagination. Lacks return structure details, but given readOnlyHint and no output schema, it is nearly complete for a retrieval 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?

Schema coverage is 100%. Description adds minimal usage context for ids/names (mutually exclusive) but does not enhance understanding of limit, page, or excludeCreatedByMonday beyond 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 clearly states the verb 'Retrieve' and the resource 'account-level object schemas', specifies filtering by IDs or names, and distinguishes from sibling tools like create/delete/update_object_schema.

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 explains when to filter vs list all (paginated), but lacks explicit guidance on when not to use this tool or alternatives (e.g., for modifying schemas).

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