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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety behavior is covered. The description adds useful scope context by saying results are official counts/faults and not an accessibility guarantee, but it does not discuss auth needs, rate limits, pagination, or freshness of fault data.

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 compact sentences: the first front-loads what is returned and its optional filters, and the second adds a clear scope disclaimer. No filler or repetition.

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?

The tool is read-only per annotations and has no output schema, so the description should carry more weight for return shape and filtering behavior. It adequately says counts and fault details are returned, but the undocumented limit and lack of return structure or pagination details leave gaps for an agent invoking it with optional parameters.

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 0% for all four parameters. The description names three filters (line, station, equipment_type) but gives no format, accepted values, or examples, and omits the limit parameter entirely, leaving meaningful semantics undocumented.

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?

States a specific action and resource: returns official Metro İstanbul equipment/total counts and current equipment fault details. The tool name suggests accessibility, but the description explicitly clarifies the narrower equipment/fault scope and adds a disclaimer, so an agent can distinguish it from a general accessibility guarantee, though not directly from siblings like transport_disruptions.

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?

Mentions optional filtering by line, station, or equipment type, which implies usage for narrowed lookups. However, it does not state when to choose this over sibling tools such as istanbul_transport_disruptions or istanbul_gtfs_snapshot_status, and no when-not guidance is given beyond the accessibility disclaimer.

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