mdl_search_people

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that – no indication of result caps, pagination limits, or that an empty query is permitted (default '').

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?

It is short and front-loaded, but this is under-specification rather than conciseness – a two-word fragment that omits every fact an agent needs. Length is fine; content is not earning its place because there is so little of it.

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?

No output schema exists, so the description should describe what a match returns (person ids, names, avatars) but does not. Combined with zero parameter documentation and no usage context, the definition is inadequate for a tool sitting among ~90 siblings.

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% for both parameters, so the description must compensate and does not. 'Query' has an empty-string default and 'Page' has a range up to 100000, yet neither the matching semantics (name? username?) nor pagination behavior is explained anywhere.

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 fragment 'Search: people' does state a verb and resource, so an agent can infer it queries people. However it offers no scope detail or differentiation from the many sibling search tools (mdl_search_titles, mdl_search_top_dramas), leaving the agent to guess what entity set 'people' covers.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. With nearly 90 sibling tools the agent gets no help deciding when this search is the right entry point versus generic search or person-lookup tools like mdl_users_get_person.

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