ebi-pdbe-sec_struct_ent_sec_struct_id_entity_id_04ac5bc3

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful content context (external-tool predictions with scores, labels, and source metadata) but says nothing about response size, per-residue volume, or why idempotentHint is false for a read operation.

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?

A single front-loaded sentence that packs the resource, scope, and payload without filler. It is dense but every clause carries information; only the parenthetical examples are slightly expendable.

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?

With no output schema, the description carries the burden of describing return values, and it does so adequately by naming helices, strands, and per-residue predictions with scores and source metadata. Missing only volume/format expectations for what could be a large per-residue payload.

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 100% for both parameters, so the schema already documents pdb_id and entity_id. The description only restates 'specified PDB Entity ID' and adds no format, pattern, or cross-parameter 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?

The description opens with a specific verb and resource ('Returns secondary-structure annotations for a specified PDB Entity ID') and enumerates the payload (helices, strands, per-residue predictions). That is enough to separate it from sibling annotation tools such as annot_ent or doms_ent, though it never names a sibling explicitly.

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 or when-not-to-use guidance and no mention of alternatives among the many entity-scoped siblings (annot, doms, chains, var, bind_sites). The only usage signal is the implicit 'requires a PDB Entity ID', which the schema already states.

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