accessibility_declarations__create

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

The description only repeats 'create' which is already obvious from the name. Annotations indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), but the description adds no additional behavioral context such as idempotency, side effects, or any constraints like 'declaration must be unique per app and device family'.

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 concise, one sentence plus the HTTP endpoint. No wasted words. The essential information is front-loaded.

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 complex nested schema (required relationships, attributes, enums) and the lack of an output schema, the description is insufficient. It does not explain the return value, error conditions, or constraints like 'only one declaration per app and device family'. The agent would need to infer usage from the schema alone.

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% (body parameter has a description), but the tool description does not explain the parameters. The schema itself is self-documenting with required fields and enums, so the baseline is 3. The description adds no additional meaning 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?

Description clearly specifies the action ('Create') and resource ('accessibility declaration'). The HTTP method/path provides further context. However, it does not explicitly differentiate from sibling tools like accessibility_declarations__update or accessibility_declarations__delete, though the verb 'create' inherently distinguishes it.

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 (e.g., update, delete, or list endpoints). There is no mention of prerequisites, such as requiring an existing app ID or that this declaration can only be created once per app and device family.

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