sendle_get_quote

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

No annotations; description is minimal and does not disclose behavioral traits such as need for an API key, rate limits, or response format. The `api_key` parameter exists in the schema but is not mentioned in the description.

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?

Extremely short (5 words), but lacks structure and valuable information beyond the tool name. It is under-specified rather than helpfully concise.

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 9 parameters, no annotations, no output schema, and 0% schema coverage, the description is woefully incomplete. Does not clarify what the quote contains or any constraints.

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 0%, meaning no parameter descriptions in schema. The description adds no information about the meaning or format of parameters like suburb, postcode, country, or weight_units.

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 'Get a shipping quote from Sendle,' specifying a clear verb+resource combination. It distinguishes from sibling tools like 'sendle_create_order' and 'sendle_track_parcel'.

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 on when to use this tool versus alternatives, no prerequisites mentioned, and no exclusions provided.

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